<text><span class="style2"> will briefly describe the Dock TOOLS collection, which includes </span><span class="style11"><a href="#" class="group">Dock Export</a></span><span class="style2">, </span><span class="style11"><a href="#" class="group">Dock Import</a></span><span class="style2">, </span><span class="style11"><a href="#" class="group">Dock Procs</a></span><span class="style2">, and </span><span class="style11"><a href="#" class="group">Dock Tables</a></span><span class="style2">. Each card in the collection is for processing information and is </span><span class="style32">not</span><span class="style2"> intended for long–term storage or accumulation of text or data.GeneralThe tools described here offer support in specific situations which arise in hypertext. They are not simple. First–time users should make backups before using the tools. While nothing of significance will happen without warning, a few mouse clicks followed by an “OK” may have a large scale effect (such as printing a 5000 page archive). Tools are frequently revised, and I am only maintaining the English version.</span></text>
</content>
<content>
<layer>background</layer>
<id>98</id>
<text>Dock Tools</text>
</content>
<name>Utility Stacks</name>
<script></script>
</card>
card_2500.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style11"><a href="#" class="group">xport</a></span><span class="style2"> is for printing, and exporting ASCII text. ASCII text can be edited and printed with any word processor.</span><span class="style23">Print Reports</span><span class="style2"> works in it’s initial configuration with all DOCK </span><span class="style11"><a href="#" class="group">standard document</a></span><span class="style2"> layouts. With Dock Layouts, cards are numbered and the numbers also appear in a table of contents, and in an index. You may also use other layouts, as long as you include their named report templates in the corresponding list.</span><span class="style31"></span><span class="style23">Export Stacks</span><span class="style2"> and </span><span class="style23">Depth–first</span><span class="style2"> produce ASCII text. Export Stacks works with any stacks included in the list. Be sure to include all the field names for your text. As for “Print Reports”, you may produce an index and a table of contents. You may also label cards and stacks in the exported text and re–import the text with “</span><span class="style11"><a href="#" class="group">Dock Import</a></span><span class="style2">” after modification with a word processor.There are many options for controlling input and output. Export may be associated with other Dock utilities. Input a selection of marked cards by running a </span><span class="style11"><a href="#" class="group">Model Probe</a></span><span class="style2"> search first. ASCII text prepared with stack and card labels is ready to move back into stacks with </span><span class="style11"><a href="#" class="group">Dock Import</a></span><span class="style2">.</span></text>
<text><span class="style2">oot StackAny Dock document may be called as a Root, because of the presence of stack catalogs. The stack called doesn’t have to be a Context Root. The export sequence is calculated directly from the tree, and doesn’t involve the currently loaded Context. The tree is developped breadth–first.Field ListYou may list several field names here. The program will export data from listed fields in the order listed. All stacks don’t need to have all fields. It is recommended that you only export non–shared fields, since shared fields play a role in hypertext which has no equivalent in the paper world.</span><span class="style35"></span></text>
</content>
<name>Dock Export Options</name>
<script></script>
</card>
card_8109.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This option exports text as a tree starting with a Root stack. The “Stacks” list isn’t involved here. The root must be a standard document format. The Root needn’t be an actual Context Root. The current Context isn’t involved in this procedure. A tree is constructed from the Catalog field, similar to what is done for Context definition.There are two ways to export text: Depth–first or breadth–first. The main export routines follow the latter pattern, which keeps texts of a stack together. Here, the export goes depth–first, similarly to what an idea processor would do. This may be useful when the FIELD list is empty, for creating an outline representation of the hypertext.</text>
</content>
<name>Depth–First</name>
<script></script>
</card>
card_7283.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>You may list several Report Templates here. The program will choose the first one it finds in each stack, in the order listed here. In the default list compatible with all DOCK standard documents, “Le Texte 1” has 1 column, “Le Texte 2” has 2 columns. This, regardless of how many columns are displayed in layouts.If you want to print 2 columns, put “Le Texte 2” in first position.If you are printing from generic stacks, make sure that they have appropriate report templates, and that the templates are listed in the Export utility.</text>
</content>
<name>Report Templates</name>
<script></script>
</card>
card_7724.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style11"><a href="#" class="group">mport</a></span><span class="style2"> moves existing text saved in the ASCII format into HyperCard stacks. How this is done depends on the text.• </span><span class="style11"><a href="#" class="group">Unformatted Import</a></span><span class="style2">: This is for short text or for text you haven’t yet read. This is almost the same as </span><span class="style11"><a href="#" class="group">standard Import</a></span><span class="style2"> with the ACT menu (Ctrl—U). The main difference is that you can specify a title field for import to generic stacks. Otherwise, using the import utility instead of the menu may be convenient for setting up standard receiving areas for import from, say, different Internet servers.• </span><span class="style11"><a href="#" class="group">Formatted Import</a></span><span class="style2">: This is when you have a longish text and you already have a clear idea of how you want the text to look in HyperCard.</span></text>
</content>
<content>
<layer>background</layer>
<id>9</id>
<text>"Import" "Dock Tools" "Import"</text>
</content>
<name>DOCK Import</name>
<script></script>
</card>
card_2231.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style30">odel Stack</span><span class="style2">: Choose a model stack for Formatted import.</span><span class="style30">Import Fields</span><span class="style2">: Choose one or more named fields in the stack to receive the text from the file.</span><span class="style30">Title field</span><span class="style2">: This may also be designated, if one is available in the format you are working with. The content is usually the same, but is separate from the card name which is always filled during import, even when no title field is given.Default settings are for </span><span class="style11"><a href="#" class="group">standard documents</a></span><span class="style2">.Note: The field descriptions are important for both unformatted and formatted import. With unformatted import, a model stack is not used, but the import routine still has to know where to place incoming information.</span></text>
</content>
<name>Stack Settings for Import</name>
<script></script>
</card>
card_6951.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style2">nformatted import may apply to unknown text which you would like to move into HyperCard stacks. This is often appropriate when you are dealing with text coming in through the phone lines. You may even import such text before you read it.</span><span class="style34"></span><span class="style2">This kind of import is very fast and very crude. The text is simply chopped into 25K segments. Since you can’t place more than 30K in a HyperCard field, the segment size is chosen such that you don’t pack the field so tight you can’t budge. Segmenting doesn’t chop at in appropriate positions, say after paragraphs. It just takes 25K chunks. The card name is the same as the text file name. If several cards are used for the same file, the same card name is repeated throughout the series.• Enter the receiving stack in the list under the “Unformatted” heading (or Shift–click on an empty line in the locked list). Click on the name in the locked list to begin import to the stack. Import adds new cards at the end of the stack. The stack isn’t checked for existing cards with the same name. Stacks receiving unformatted import remain in the windows.See also: </span><span class="style11"><a href="#" class="group">Standard Import</a></span><span class="style2">.</span></text>
</content>
<name>Unformatted Import</name>
<script></script>
</card>
card_5660.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style2">ext import is a frequently discussed issue in hypertext. Formatted import is complex. Export from HyperCard is fairly straightforward in the sense that any hypertext, no matter how convoluted, can be boiled down to a list. The list can be represented as a two–tier outline with, say, sections for stacks, and paragraphs for cards. Whether this is always appropriate or does justice to the hypertext is beside the point, the export can be acheived simply and without too much soul–searching.</span><span class="style34"></span><span class="style2">Ordinary text, on the other hand, may not have the two–tier structure required to become HyperCard stacks. Anyone who has used an outliner knows how wonderful it is to have nested paragraphs indented so far to the right that they go marching off the edge of the page. The hypertext equivalent of this exists, of course. In Dock hypertext, an outline </span><span class="style11"><a href="#" class="group">Tree</a></span><span class="style2"> is constructed with the Catalog fields. In practice, however, the paradigm is totally different. The traditional outline always takes the reader into the depth while the HyperCard stack leads the reader along a level.“Automagic” translation schemes are easy to write but they rarely—if ever—produce the effect you want. This will explain, I hope, why I have chosen a formatted import scheme where the text to import has to be prepped according the HyperCard paradigm.</span></text>
</content>
<name>Formatted Import</name>
<script></script>
</card>
card_6321.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style2">hen the ASCII text file to be imported has a known—an possibly complex—structure, the easiest way to move the text to HyperCard stacks is to indicate where the text’s articulations are in the ASCII file, prior to import*.</span><span class="style34"></span><span class="style30">Strings to Find in ASCII File</span><span class="style2">: “Start new stack after” is the label which must preceed each new stack name in the text file. “Start new card after” is the label which preceeds card names. The “Next field after” string, if used, causes import to skip to the next listed field. All these strings should be chosen such that there is no chance of finding them used for other purposes.</span><span class="style34"></span><span class="style2">The name can be placed on the same line as or on the line following the label.</span><span class="style34"></span><span class="style2">If you use the the “Next field after” string, don’t include field names in the text file, they will be accessed in order from the “Field[s] for main text” list.</span><span class="style34"></span><span class="style2">* You can use a word processor or HyperCard to prep text. See </span><span class="style11"><a href="#" class="group">Dock Export</a></span><span class="style2"> for more information about moving text from HyperCard to ASCII files. Well–planned use of Export/Import can bring about radical restructuring of HyperCard archives. Radical restructuring means you should make backups before you begin.</span></text>
</content>
<content>
<layer>background</layer>
<id>9</id>
<text>"Import" "Dock Tools" "Import"</text>
</content>
<name>Preparing ASCII File for Import</name>
<script></script>
</card>
card_5446.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput the visible of card field short name of me into thePropset the visible of card field short name of me to not thePropset the hilite of me to not thepropend mouseUp</script>
</part>
<part>
<id>2</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>6</left>
<top>42</top>
<right>506</right>
<bottom>293</bottom>
</rect>
<style>rectangle</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>plain</textStyle>
<textHeight>13</textHeight>
<name>Example Text</name>
<script></script>
</part>
<content>
<layer>background</layer>
<id>10</id>
<text>Stack Creation During Import</text>
</content>
<content>
<layer>background</layer>
<id>56</id>
<text>13/11/942867567109</text>
</content>
<content>
<layer>background</layer>
<id>40</id>
<text>30/10/942866385092</text>
</content>
<content>
<layer>background</layer>
<id>116</id>
<text>25</text>
</content>
<content>
<layer>background</layer>
<id>71</id>
<text>Randy Ayling</text>
</content>
<content>
<layer>background</layer>
<id>39</id>
<text>11/14 </text>
</content>
<content>
<layer>background</layer>
<id>38</id>
<text><span class="style2">hen you import prepared ASCII text, the text itself determines which stacks to use for the import. If the stacks are not found in the folder containing the ASCII text, they are created. Any stacks outside the folder containing the text are ignored. This means that files should be carefully positioned in the Finder hierarchy for formatted input. The bothersome “same folder” constraint is intended to prevent surprises (like erasing stacks you want to keep). Make backups first!</span><span class="style23">Use Existing Stacks</span><span class="style2">: If an existing stack is found in the import folder, the program will replace the text on the appropriate cards. Any fields not listed in the import utility are left untouched. Of course, the existing stack must have at least one of the listed fields. New cards may be added after the first card, but no cards are deleted.</span><span class="style34"></span><span class="style23">Replace Existing Stacks</span><span class="style2">: The program simply creates a new stack after destroying any existing one with the same name in the folder which contains the ASCII text.</span><span class="style34"></span><span class="style23">Ask</span><span class="style2">: This option makes the program pause with a dialog if it encounters an existing version of a stack, so you can decide on a case by case basis whether you want to use a stack or replace it.</span></text>
</content>
<content>
<layer>card</layer>
<id>2</id>
<text>\stack\Test stack 1\card\NoteThis text is also included as an ASCII text document in the “Dock Tools” folder and demonstrates the use of the Dock Import facility, using the default settings.\stack\Test Stack 2\card\Motivation\field\Obviously, there is a great deal of text material “out there”, some of which may be useful as hypertext. Existing text most commonly occurs as word processing documents.\card\AdvantagesThe original text file will require some preliminary editing, but the advantages of importing text versus cutting and pasting can be overwhelming, especially if you have a lot of text. On the down side, all character styles are lost in the ASCII format.\field\One other point which needs to be made is that you may prefer to write using a word processor, even if your real objective is to place your text in HyperCard stacks. Dock Import makes this easy to do.</text>
</content>
<content>
<layer>background</layer>
<id>9</id>
<text>"Import" "Dock Tools"</text>
</content>
<name>Stack Creation During Import</name>
<script></script>
</card>
card_7514.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style2">he special case of formats with columns</span><span class="style23">Next field after</span><span class="style2"> stringThis works with text displayed in several columns. You may use the </span><span class="style11"><a href="#" class="group">Model Document with 2 Columns</a></span><span class="style2"> stack as the “Model Stack” to demonstrate this capability. You can use the string to skip fields. If more “Next field after” strings are encountered than there are listed fields, the text simply continues to accumulate in the last field.</span></text>
</content>
<name>Multiple Field Formatted Import</name>
<script></script>
</card>
card_5188.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style11"><a href="#" class="group">ables</a></span><span class="style2"> converts TAB—delimited text into SPACE—delimited text.This works with mono–spaced fonts like “</span><span class="style28">Monaco</span><span class="style2">” and “</span><span class="style29">Courier</span><span class="style2">”.• Paste the text to convert into the upper field.• Lay out TAB stops in the MacWrite–like ruler in the middle • Click on the stop on the far left to get a new stop • Drag any stop downward to delete it• Click on the “APPLY” button</span><span class="style17"></span><span class="style2">Converted text appears in the lower fieldCheck “Squeeze” to run the text together, ignoring tabs.Check “Group” to group the words of each column for overviews.The peculiar–looking alignments behind the “Reorganize” button and the “Include” label are spreadsheet devices for rearranging columns. You may find them useful, mainly because they can save you a trip to a real spreadsheet program.</span></text>
</content>
<content>
<layer>background</layer>
<id>9</id>
<text>"Tables" "Dock Tools"</text>
</content>
<name>Dock Tables</name>
<script></script>
</card>
card_4875.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style11"><a href="#" class="group">rocs</a></span><span class="style2"> is a collection of programs dedicated to batch processing of hypertext documents. All routines apply to listed stacks. When in doubt, make backups before batching.</span><span class="style23">Default font</span><span class="style2">: Sets the default font in all background fields.</span><span class="style23">Field Style</span><span class="style2">: Sets the style of field(s).</span><span class="style23">Card Info</span><span class="style2">: Changes the info on each card in Dock formats. Dock hypertext documents record the User Name from the </span><span class="style11"><a href="#" class="group">Home</a></span><span class="style2"> stack in a “Card Info” field. The field can be used for any keyword. “Add Text Before” creates a new line if the text ends with a return. “After” creates a new line if the text starts with a return.</span><span class="style23">Compact stacks</span><span class="style2">: Compacts all stacks and locks fields for navigation. This is usually a prelude to shipping hypertext to other people.Remark: Selections from </span><span class="style32">On Location</span><span class="style2"> can be pasted directly into the </span><span class="style32">Procs</span><span class="style2"> list and they will be automatically stripped down to bare file names.</span></text>
